린 소프트웨어 개발 (책)

Forewords by Jim Highsmith, Ken Schwaber

Foreword by Jim Highsmith

Foreword by Ken Schwaber

Preface

Introduction

Statewide Automated Child Welfare Information System

Guided tour:

1. Eliminate waste
2. Amplify learning
3. Decide as late as possible
4. Deliver as fast as possible
5. Empower the team
6. Build integrity in
7. See the whole

Chapter 1. Eliminate waste

Tools:

• Tool 1: Seeing waste
• Tool 2: Value stream mapping

Chapter 2. Amplify learning

Tools:

• Tool 3: Feedback
• Tool 4: Iteration
• Tool 5: Synchronization
• Tool 6: Set-based development

Chapter 3. Decide as late as possible

Tools:

• Tool 7: Options thinking
• Tool 8: The Last responsible moment
• Tool 9: Making decisions

Chapter 4. Deliver as fast as possible

Tools:

• Tool 10. Pull system
• Tool 11. Queuing theory
• Tool 12. Cost of delay

Chapter 5. Empower the team

Tools:

• Tool 13. Self determination
• Tool 14. Motivation
• Tool 15. Leadership
• Tool 16. Expertise

Chapter 6. Build integrity in

Tools:

• Tool 17: Perceived integrity
• Tool 18: Conceptual integrity
• Tool 19: Refactoring
• Tool 20: Testing

Chapter 7. See the whole

Tools:

• Tools 21: Measurements
• Tools 22: Software contracts

Chapter 8. Instructions And Warranty

The balance point of the lean principles:

If today’s problems come from yesterday’s solutions, hen tomorrow’s problems will come from today’s solutions. Avoid creating a pendulum that swings from high ceremony to low ceremony and back; look for the balance point of the lean principles:

• Eliminate waste does not mean throw away all documentation.
• Amplify learning does not mean keep on changing your mind.
• Decide as late as possible does not mean procrastinate.
• Deliver as fast as possible does not mean rush and do sloppy work.
• Empower the team does not mean abandon leadership.
• Build integrity in does not mean big design up front.
• See the whole does not mean ignore the details. —p179